Detect MCP server connection failures in Copilot debug logs#9604
Closed
Detect MCP server connection failures in Copilot debug logs#9604
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update MCP server connection error handling in log handler
Detect MCP server connection failures in Copilot debug logs
Jan 11, 2026
Contributor
|
@copilot when you detect a mcp failure, you should fail the step in parseDebugLogFormat |
…bugLogFormat Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Contributor
|
💀 Blimey! Changeset Generator failed and walked the plank! No treasure today, matey! ☠️ |
Contributor
|
🎬 THE END — Smoke Claude MISSION: ACCOMPLISHED! The hero saves the day! ✨ |
Contributor
|
✨ The prophecy is fulfilled... Smoke Codex has completed its mystical journey. The stars align. 🌟 |
Contributor
|
📰 VERDICT: Smoke Copilot has concluded. All systems operational. This is a developing story. 🎤 |
Contributor
Smoke Test Results (Claude)Last 2 merged PRs:
Test Results:
Overall Status: PARTIAL PASS (4/6 tests passed)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Copilot log parser was not detecting MCP server connection failures, allowing workflows to continue running with unavailable tools instead of failing fast with actionable error messages.
Changes
Modified
parseDebugLogFormat(): Scans debug logs for MCP connection errors using pattern[ERROR] Failed to start MCP client for remote server <name>: TypeError: fetch failed, extracts server names, and immediately callscore.setFailed()to fail the step when failures are detectedUpdated
parseCopilotLog(): Propagates MCP failures from debug log parsing into result object for consistencyAdded test coverage: 5 test cases covering single/multiple failures, successful connections, deduplication, and verification that
core.setFailed()is called with the correct error messageBehavior
Without MCP failures,
mcpFailuresis undefined and execution continues normally. The step fails immediately during log parsing rather than later in the bootstrap layer, providing faster feedback about MCP connection issues.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.